Flow.Launcher/ViewModel/PluginStoreItemViewModel.cs (1)

44-64: ⚠️ Potential issue | 🟠 Major

Potential null reference issue with nullable DateTime arithmetic.

_newPlugin.LatestReleaseDate and _newPlugin.DateAdded are DateTime? (per UserPlugin.cs lines 68-73). Subtracting a nullable DateTime? from DateTime.Now without null checks can cause runtime exceptions or undefined behavior when these values are null.

🛠️ Proposed fix with null checks

 public string DefaultCategory
 {
     get
     {
         string category = None;
-        if (DateTime.Now - _newPlugin.LatestReleaseDate < TimeSpan.FromDays(7))
+        if (_newPlugin.LatestReleaseDate.HasValue && 
+            DateTime.Now - _newPlugin.LatestReleaseDate.Value < TimeSpan.FromDays(7))
         {
             category = RecentlyUpdated;
         }
-        if (DateTime.Now - _newPlugin.DateAdded < TimeSpan.FromDays(7))
+        if (_newPlugin.DateAdded.HasValue && 
+            DateTime.Now - _newPlugin.DateAdded.Value < TimeSpan.FromDays(7))
         {
             category = NewRelease;
         }
         if (_oldPluginPair != null)
         {
             category = Installed;
         }

         return category;
     }
 }

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@Flow.Launcher/ViewModel/PluginStoreItemViewModel.cs` around lines 44 - 64,
The DefaultCategory getter performs DateTime.Now - _newPlugin.LatestReleaseDate
and DateTime.Now - _newPlugin.DateAdded where those fields are nullable
(DateTime?); guard these uses by checking _newPlugin.LatestReleaseDate.HasValue
and _newPlugin.DateAdded.HasValue (or using GetValueOrDefault with an existence
check) before doing the subtraction, and only assign RecentlyUpdated/NewRelease
when the corresponding nullable has a value; keep the existing logic around
_oldPluginPair and the returned category intact.